Data Profiles is a Replenishment concept that is used for defining which calculation rules are used for which Items or Item-Store combinations. This information is stored in the Item table or the Item-Store Record which can be maintained on the Replenishment Control Data Page.
Data profiles can be assigned manually to Items and Item-Store Records or default values from Item Categories and/or Retail Product Groups are applied.
Hierarchy Relations also let you define data profiles to relations and to update the relevant tables manually or via Scheduler Job.
To edit a Hierarchy Relation for data profile maintenance
- Click the
icon, enter Hierarchy Relation, and select the relevant link. - Select a Hierarchy Relation with Usage Type Assortment, and click the Edit Hierarchy Relation action.
Note: This page has the same functionality as described in How to: Edit Hierarchy Relations. This page, however, has one more field, Default Distribution Pattern, in the General FastTab and two more functions under the Replenishment action menu, Update Item Distribution and Update Data Profiles. In the right Hierarchy Viewer FastTab, there are three more fields: Distribution Pattern, Dimension Pattern Code, and Replen. Data Profile Code.
To add a Replenishment data profile to a relation
- Select the node in the right Hierarchy Viewer FastTab.
- Change the Replen. Data Profile Code field in the Line.
- On the request page, click Yes, if you want to update the field for this node and all child nodes.
- On the request page, click No, if you want to update the field for this node only.
Note: Replen. Data Profile Code and Item Distribution can be maintained in one Hierarchy Relation or two separate Hierarchy Relations. If you work with two separate Hierarchy Relations, we recommended to create a relation between the nodes where you intend to set up the data profiles. This may vary from the relations that are used in the Hierarchy Relation for the Item Distribution.
Special setup scenarios
Detailed setup (Item-Store Record only)
In a detailed setup you assign your data profiles to Item-Store Records only. This is achieved with the below setup:
In this scenario you create a relation between the nodes A ITEMS and the store nodes BIG, MEDIUM, and SMALL. The linked entities (Stores S0001, S0002, ...) inherit the settings.
When you create the data profile for that Hierarchy Relation, the result for item 1000 is:
The system creates five lines in the Item Store Records and the Replen. Data Profile field on the Replenishment Control Data page remains empty.
Generic setup (Replenishment control data only)
In a generic setup scenario, you assign your data profiles to Item records only. This is achieved with the below setup:
In this scenario you have a relation between the node B ITEMS and the store node ALL STORES, and the Replen. Data Profile Code field is filled with the Data Profile STOCK_GEN.
Note: The Replen. Data Profile Code is not inherited down to the child nodes.
When you enter the value in the Replen. Data Profile Code field, the system asks if you want to update the child nodes.
To store the value only for the current node, without inheritance, click No.
When you create the data profile for that Hierarchy Relation, the result for item 1100 is:
The system creates no lines in the Item Store Records and the Replen. Data Profile field on the Replenishment Control Data page is filled. This approach should be applied when no store-specific data profiles are needed.
Note: In the above examples the node ALL STORES updates the Replenishment Control Data while the other nodes update the Item Store Records.
This behavior is controlled by the Hierarchy Node for all Stores (no Filter) field on the Replenishment Setup page.
Mixed setup (Replenishment control data and Item-Store records)
In a mixed setup scenario, you assign your data profiles to Item records and Item-Store Records (for exceptions). This is achieved with the below setup:
In this scenario you have a relation between the node A ITEMS and the store node ALL STORES, and the Replen. Data Profile Code field is filled with the data profile AVG_GEN.
Note: There is also a setup for the Replen. Data Profile Code for the node MEDIUM, which includes the Stores S0003 and S0004.
When you create the data profile for that Hierarchy Relation the result for item 1000 is:
The system creates two lines in the Item Store Records and the Replen. Data Profile field on the Replenishment Control Data page is filled. This approach should be applied when a generic rule exists but also exceptions.
Warehouse setup (Item-Store records)
In the warehouse setup scenario, you assign your data profiles to Item-Store Records (for Warehouse Locations). This is achieved with the below setup:
In this scenario you have a relation between the node A ITEMS and the store node WAREHOUSES, and the Replen. Data Profile Code field is filled with the data profile STOCK_WHSE.Note: The node WAREHOUSES has links to the warehouses W0001 and W0002.
When you create the data profile for that Hierarchy Relation, the result for item 1000 is:
The system creates four lines in the Item Store Records and the Replen. Data Profile field on the Replenishment Control Data page is filled. This approach is used, if you need specific settings for the Warehouse Locations, such as Reorder Point or Maximum Quantity.
Note: Not all Replenishment Calculation Types are supported for Warehouse Locations. Make sure to use the correct calculation type in the Data Profile. If you assign an unsupported calculation type, the system will change it to calculation type Stock Level by default.